Feature/function arg wrapping #1127
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A second PR from me, but still haven't had one merged so definitely need to get the contributor stuff sorted, etc
This PR is to address issues that seem to have been raised in #590 and #978. basically when there are function calls with argument lists nested inside function calls with argument lists, yapf refuses to consider splitting the secondary argument lists which leads to it ignoring the penalty for splitting before the first argument or showing different behavior when arguments are functions vs not functions.
This PR tries to address this in as minimally invasive a way as possible by recursively calculating the length of nested function arguments and calculating whether it is possible to wrap them. This doesn't actually modify any of the wrapping logic, so it is still up to yapf how it wants to wrap stuff, it just removes MustSplit penalties in cases where they aren't actually necessary because args could be wrapped successfully.
There are no tests for this feature, so those will obviously have to be added as well before merging.